Skip to main content

Performance & Availability Monitoring

IO River provides you the ability to monitor your CDNs for both performance and availability. IO River monitors your services from many locations around the world, providing you visibility for your service in each geolocation. In addition, these monitors can be used for routing decisions when the traffic is routed between multiple CDNs. You can use these monitors when you create traffic policies.

Monitoring URLs​

Monitoring is done on your traffic resources. You can configure URLs of your service, and these will be used for monitoring. This is important as that specific resource may behave differently than the “average” due to the content properties (static vs. dynamic, object size, connectivity to the origin, the particular configuration of the account, etc.). These resources will be periodically checked for both availability and performance.

Monitoring Sources​

IO River uses data from multiple synthetic monitoring sources to evaluate performance. The system uses the defined resource (i.e., URL) and periodically monitors it. Each CDN provider of the list-defined CDNs of your service will be checked independently. Those frequent checks allow the system to quickly identify and respond to any availability issues and provide accuracy, as those measurements are based on the specific resource of the customer.

The sources that the system uses are:

  • Cloud locations
  • IO River internal infrastructure
  • Catchpoint

IO River receives performance and availability data from those sources, aggregates the results, and concludes the customer’s service availability and performance in each geolocation.

Performance Monitoring​

When you configure a performance monitor, the configured URL is measured for Time to First Byte (TTFB). TTFB includes the following components:

  • DNS time - time it takes to resolve the CDN CNAME.
  • TCP connect time - time it takes to establish a TCP connection.
  • TLS time - time it takes to establish a secured connection.
  • Wait time - time measured from sending the HTTP request to receiving the first byte of the response.

You can view both TTFB and other measured components results in your service performance monitoring dashboard.

Availability Monitoring​

When you configure an availability monitor, the configured URL is measured for availability. IO River periodically checks that the resource returns a successful result (i.e., status code 2xx). In addition, IO River defines a timeout of 3 seconds. In case fetching the resource takes more than that, IO River considers the check as failed.

You can view the availability results in your service availability monitoring dashboard.

Geographical Coverage​

IO River's internal monitoring infrastructure covers more than 70 countries and US states, whereas certain geolocations are sampled from multiple sources (POPs). In addition, to complete the geographical coverage, IO River uses Catchpoint as an internal source to measure performance and availability. IO River also allows extended coverage in specific geolocations that might contain a substantial part of customer traffic.

Using Monitors in Traffic Policies​

When you configure traffic policies, you can use performance monitors for routing traffic based on performance and availability monitors for automatic failover between providers. More information about traffic policies can be found here.

Prerequisites​

Before adding a Monitor to your service, you need to have the following:

  • IO River Service - You can follow these steps to create a service.